Method performed by at least one server for processing a data packet from a first computing device to a second computing device to permit end-to-end encryption communication

ABSTRACT

A method (500) performed by at least one server for processing a data packet from a first computing device to be transmitted to a second computing device is disclosed, in which the data packet includes a message encrypted using a first encryption key to form an encrypted message, identification data of the second computing device encrypted using a second encryption key to form encrypted identification data, and encrypted first and second encryption keys. The method comprises decrypting (504) the encrypted second encryption key; encryption key; decrypting (506) the encrypted identification data using the decrypted second encryption key; and transmitting (508) the data packet based on the decrypted identification data, wherein the encrypted message and first encryption key are arranged to be undecryptable by the server to permit end-to-end encryption communication between the first and recipient info encryption key end-to-end encryption communication between the first and second computing devices. A related system is also disclosed.

FIELD AND BACKGROUND

The present invention relates to a method performed by at least oneserver for processing a data packet from a first computing device to asecond computing device to permit end-to-end encryption communication,and a corresponding system.

Presently, certain messaging solutions perform two differentencryption-decryption methods, for example in a scenario where a serveris arranged between two computing devices, a sender and a recipient, ina communication network. The sender encrypts a message using a symmetrickey which is randomly generated. The sender then encrypts the symmetrickey using the server's public key, and thereafter transmits a datapackage, comprising the encrypted message and symmetric key, to theserver. The server decrypts the encrypted symmetric key using its ownprivate key, after which the server then re-encrypts the symmetric keywith the recipient's public key and the re-formatted data package isforwarded to the recipient. It will be appreciated that since the serverhas the symmetric key, the server is however then able to access theencrypted message. On receiving the data package, the recipient decryptsthe encrypted symmetric key with its own private key to retrieve thesymmetric key which is used to decrypt the encrypted message. For such ascenario, the server has a copy of the symmetric key and is able todecrypt the encrypted message for audit purposes or archival of thedecrypted message. However, this is not considered true end-to-endencryption communication, since the server has access to the content ofthe message.

For other conventional implementations, the server may be configured tore-generate a new symmetric key and re-encrypt the message with the newsymmetric key, and encrypt the new symmetric key with the recipient'spublic key. In this situation, the server nonetheless still has accessto the encrypted message and thus also does not enable true end-to-endencryption communication.

One object of the present invention is therefore to address at least oneof the problems of the prior art and/or to provide a choice that isuseful in the art.

SUMMARY

According to a 1^(st) aspect of the invention, there is provided amethod performed by at least one server for processing a data packetfrom a first computing device to be transmitted to a second computingdevice, wherein the data packet includes a message encrypted using afirst encryption key to form an encrypted message, identification dataof the second computing device encrypted using a second encryption keyto form encrypted identification data, and encrypted first and secondencryption keys. The method comprises decrypting the encrypted secondencryption key; decrypting the encrypted identification data using thedecrypted second encryption key; and transmitting the data packet basedon the decrypted identification data. The encrypted message and firstencryption key are arranged to be undecryptable by the server to permitend-to-end encryption communication between the first and secondcomputing devices.

The method advantageously enables realisation of a multiple-keyencryption scheme that allows a sender to send encrypted messages to arecipient(s) by forwarding the encrypted messages through anintermediate server to perform re-routing of the data packet, but theserver is however not enabled with the ability to decrypt the encryptedmessages. This beneficially ensures that a true end-to-end encryption isachieved between the sender and the recipient(s).

Preferably, decrypting the encrypted second encryption key may includeusing a private key of the server to perform the decryption. Also,transmitting the data packet may include transmitting via an SMS, anMMS, instant messaging, an email, an attachment or an electronicdocument delivery service. The message may include text, images,animation, video or audio. It is to be appreciated that the firstencryption key may be encrypted using a public key of the secondcomputing device, or alternatively, the first encryption key may beencrypted using a public key of the server. More preferably, the secondencryption key may be encrypted using a public key of the server. Yetpreferably, the data packet may further include an initializationvector, and a digital signature generated based on the encryptedmessage.

According to a 2^(nd) aspect of the invention, there is provided amethod performed by a first computing device for processing informationto be transmitted to a second computing device via at least one serverto permit end-to-end encryption communication between the first andsecond computing devices. The method comprises encrypting a message andidentification data of the second computing device respectively usingfirst and second encryption keys; encrypting the first and secondencryption keys; and transmitting the encrypted message, identificationdata, first and second encryption keys collectively as a data packet.

Preferably, the message may include text, images, animation, video oraudio. Further, transmitting the data packet may include transmittingvia an SMS, an MMS, instant messaging, an email, an attachment or anelectronic document delivery service. More preferably, encrypting thefirst encryption key may include encrypting using an encryption key ofthe second computing device, or an encryption key of the server. Inaddition, the encryption key of the second computing device may includea public key thereof, and the encryption key of the server may include apublic key thereof. Encrypting the second encryption key may includeencrypting using an encryption key of the server. The encryption key ofthe server may include a public key thereof.

Preferably, the method may further comprise displaying an interface toenable a user of the first computing device to select the message from aplurality of messages, and the second computing device from a pluralityof computing devices able to receive the data packet. The data packetmay further include an initialization vector, and a digital signaturegenerated based on the encrypted message.

According to a 3^(rd) aspect of the invention, there is provided amethod performed by a first computing device for processing a datapacket from a second computing device forwarded via at least one serverto permit end-to-end encryption communication between the first andsecond computing devices, wherein the data packet includes a messageencrypted using a first encryption key to form an encrypted message,identification data of the first computing device encrypted using asecond encryption key to form encrypted identification data, andencrypted first and second encryption keys. The method comprisesdecrypting the encrypted first encryption key; and decrypting theencrypted message using the decrypted first encryption key to obtain themessage.

Preferably, decrypting the encrypted first encryption key may includeusing a private key of the first computing device to perform thedecryption.

According to a 4^(th) aspect of the invention, there is provided asystem for exchanging a data packet between first and second computingdevices via at least one server to permit end-to-end encryptioncommunication between the first and second computing devices. The systemcomprises the first and second computing devices, and the server. Thefirst computing device includes an encryption module for: encrypting amessage and identification data of the second computing devicerespectively using first and second encryption keys; and encrypting thefirst and second encryption keys; and a transmission module fortransmitting the encrypted message, identification data, first andsecond encryption keys collectively as the data packet to the server.The server is configured to process the data packet received from thefirst computing device and includes a decryption module for: decryptingthe encrypted second encryption key of the data packet; and decryptingthe encrypted identification data of the data packet using the decryptedsecond encryption key; and a transmission module for transmitting thedata packet to the second computing device based on the decryptedidentification data, wherein the encrypted message and first encryptionkey are arranged to be undecryptable by the server. The second computingdevice is configured to process the data packet received from the serverand includes a decryption module for: decrypting the encrypted firstencryption key of the data packet; and decrypting the encrypted messageof the data packet using the decrypted first encryption key to obtainthe message.

Preferably, the decryption module of the server may include beingconfigured to use a private key of the server to decrypt the encryptedsecond encryption key.

On the other hand, the transmission module of the server may includebeing configured to transmit the data packet using an SMS, an MMS,instant messaging, an email, an attachment or an electronic documentdelivery service. The message may include text, images, animation, videoor audio. The encryption key of the second computing device used by theencryption module of the first computing device to encrypt the, firstencryption key may preferably include a public key of the secondcomputing device.

Preferably, the encryption module, of the first computing device mayfurther be configured to encrypt the first encryption key using anencryption key of the second computing device, or an encryption key ofthe server. In addition, the encryption module of the first computingdevice may yet further be configured to encrypt the second encryptionkey using an encryption key of the server.

Preferably, the encryption key of the server used by the encryptionmodule of the first computing device to encrypt the second encryptionkey may include a public key of the server. The data packet may furtherinclude an initialization vector, and a digital signature generatedbased on the encrypted message.

According to a 5^(th) aspect of the invention, there is provided anencryption device for processing information to be transmitted to acomputing device via at least one server to permit end-to-end encryptioncommunication between the encryption and computing devices. Theencryption device comprises an encryption module for: encrypting amessage and identification data of the computing device respectivelyusing first and second encryption keys; and encrypting the first andsecond encryption keys; and a transmission module for transmitting theencrypted message, identification data, first and second encryption keyscollectively as a data packet.

According to a 6^(th) aspect of the invention, there is provided adecryption device for processing a data packet from a computing deviceforwarded via at least one server to permit end-to-end encryptioncommunication between the decryption and computing devices, wherein thedata packet includes a message encrypted using a first encryption key toform an encrypted message, identification data of the first computingdevice encrypted using a second encryption key to form encryptedidentification data, and encrypted first and second encryption keys. Thedecryption device comprises a decryption module for: decrypting theencrypted first encryption key; and decrypting the encrypted messageusing the decrypted first encryption key to obtain the message.

According to a 7^(th) aspect of the invention, there is provided amethod performed by at least one server for processing a data packetfrom a first computing device to be transmitted to a second computingdevice, wherein the data packet includes a message encrypted using afirst encryption key to form an encrypted message, identification dataof the second computing device encrypted using a second encryption keyto form encrypted identification data, an encrypted first encryption keyformed by encrypting the first encryption key using a third encryptionkey associated with the second computing device, and an encrypted secondencryption key formed by encrypting the second encryption key using anencryption key associated with the server. The method comprisesdecrypting the encrypted second encryption key; decrypting the encryptedidentification data using the decrypted second encryption key; andtransmitting the data packet based on the decrypted identification data.The encrypted first encryption key is arranged to be decryptable onlyusing a fourth encryption key associated with the second computingdevice; and the third and fourth encryption keys of the second computingdevice are configured as a pair of asymmetric keys.

Preferably, the encryption key associated with the server may include apublic key of the server. Following on, decrypting the encrypted secondencryption key may include using a private key of the server to performthe decryption. Further, transmitting the data packet may includetransmitting via an SMS, an MMS, instant messaging, an email, anattachment or an electronic document delivery service. The message mayinclude text, images, animation, video or audio. Yet preferably, thethird and fourth encryption keys respectively may include a public keyand a private key of the second computing device. The data packet mayfurther include an initialization vector, and a digital signaturegenerated based on the encrypted message.

It should be apparent that features relating to one aspect of theinvention may also be applicable to the other aspects of the invention.

These and other aspects of the invention will be apparent from andelucidated with reference to the embodiments described hereinafter.

BRIEF DESCRIPTION OF THE DRAWINGS

Embodiments of the invention are disclosed hereinafter with reference tothe accompanying drawings, in which:

FIG. 1 is a schematic diagram depicting a system for exchanging a datapacket between first and second computing devices via a server to permitend-to-end encryption communication, according to an embodiment of thepresent invention;

FIG. 2, includes FIGS. 2a to 2c , shows the configurations of the firstand second computing devices, and the server of FIG. 1;

FIG. 3 is a flow diagram of a method performed by the first computingdevice of FIG. 1 for processing information to be transmitted to thesecond computing device as the data packet;

FIG. 4 shows a format of the data packet;

FIG. 5 is a flow diagram of a method performed by the server of FIG. 1for processing the data packet received from the first computing device;and

FIG. 6 is a flow diagram of a method performed by the second computingdevice of FIG. 1 for processing the data packet received from theserver.

DETAILED DESCRIPTION OF PREFERRED EMBODIMENTS

A system 100 (i.e. see FIG. 1) and corresponding method 500 (i.e. seeFIG. 5) for exchanging a data packet 102 between first and secondcomputing devices 104, 106 (i.e. two parties) via at least one server108 to permit end-to-end encryption communication is disclosed,according to a first embodiment. The system 100 includes the first andsecond computing devices 104, 106, and the server 108, which isconfigurationally arranged intermediate to the first and secondcomputing devices 104, 106. It is to be appreciated that the server 108is configured with associated public key and private key, as per thepublic-key infrastructure (i.e. asymmetric keys cryptography)terminology. Similarly, the second computing device 106 is alsoconfigured with associated public key and private key. In the context ofFIG. 1, the first computing device 104 is a sender of the data packet102, and the second computing device 106 is an eventual intendedrecipient of the data packet 102. But it will also be appreciated thatthe opposite relationship is possible in other instances, i.e. thesecond computing device 106 becomes the sender, while the firstcomputing device 104 becomes the recipient. In particular, the system100 enables true end-to-end encryption communication between the senderand recipient, while still allowing the server 108 to route the datapacket 102 in a secure manner, but without being able to decrypt asecure message embedded in the data packet 102 to access the contents ofthe message. Also for sake of simplicity in illustrating and describing,only one server 102 is shown in FIG. 1, although it will be understoodthat the data packet 102 may be forwarded through multiple servers 108(i.e. a server cluster) before being received by the second computingdevice 106. In the said scenario of multiple servers 108, it is to beappreciated that each of the servers 108 is configured to have access toa common set of public key and private key (e.g. which may be storedlocally on each server 108, or be stored on a storage server equallyaccessible by all the multiple servers 108). Specifically, the commonset of public key and private key is to be used for the purpose ofencrypting and decrypting identification data of the second computingdevice 106, which will be elaborated below. It is further to beappreciated that the first and second computing devices 104, 106, andthe server 108 resides in a communication network.

Examples of the first and second computing devices 104, 106 includemobile computing devices (e.g. smartphones like iPhone™ or tablets likeiPad™), wired computers (e.g. desktop personal computers) or the like.However, for the purpose of this embodiment, the first and secondcomputing devices 104, 106 are mobile computing devices running on apredetermined suitable mobile operating system (e.g. iOS™ from AppleInc™). For ease of referencing hereinafter, the first and secondcomputing devices 104, 106 are respectively referred to as theencryption device 104 and the decryption device 106 (in the context oftrue end-to-end encryption communication relationship), unless otherwiseexplicitly stated. It will also be appreciated that there can bemultiple encryption devices 104 and decryption devices 106 arrangedwithin the system 100 in the communication network to exchange differentdata packets 102 with one another, but not however specifically shown inFIG. 1 in this instance, for sake of brevity. As for the server 108,examples include any types of server suitably configured for performingthe task of routing the data packet 102 between the encryption device104 and decryption device 106.

Referring to FIG. 2, the encryption device 104 is configured to executean encryption program code (not shown) for processing information intothe data packet 102 to be provided to the decryption device 106, whereasthe decryption device 106 is configured to execute a decryption programcode (not shown) for processing the received data packet 102. On theother hand, the server 108 is configured to execute a data-packetprocessing code (not shown), which is based on the method 500 of FIG. 5,for processing the data packet 102 sent by the encryption device 104 tothe decryption device 106. It will be appreciated that, in thisembodiment, the encryption and decryption program codes are locallyinstalled on the encryption device and decryption device 104, 106, andfurther, the encryption and decryption program codes are realised asnative mobile applications (e.g. as a software usable by users).Specifically, the encryption device 104 includes the following modules:an encryption module 1042, a display module 1046, a transmission module1048 and a processor module 10410, while the decryption device 106includes the following modules: a receiver module 1062, and a decryptionmodule 1064. Similarly, the data-packet processing code is implementedas an application specific program (which may be configured to run as abackground process) and locally installed on the server 108. For theserver 108, the following modules are arranged therewithin: a receivermodule 1082, a decryption module 1084, and a transmission module 1086.In this instance, it is to be understood that the respective saidmodules of the encryption device 204 and decryption device 206 areimplemented in software, and thus are incorporated respectively into theencryption program code and decryption program code. This appliesmutatis mutandis to the said modules of the server 108.

Reference is now made to FIGS. 3 and 4 to describe a method 300performed by the encryption device 104 (i.e. the sender) for processinginformation to be transmitted to the decryption device 106 (i.e. therecipient) via the server 108 to permit end-to-end encryptioncommunication. At step 302 of the method 300, the display module 1046 isarranged to display a software interface (not shown) to enable a user(not shown) of the encryption device 104 to select a desired message(i.e. input data) from a plurality of messages to be sent to thedecryption device 106. It will be appreciated that the message includestext, images, animation, video, audio or the like. In addition, at thestep 302, the user also uses the software interface to select arecipient (from a plurality of devices) of the selected message, whichin this context is the decryption device 106. Further, the interfacealso displays an option on whether end-to-end encryption is desired bythe user. If the user selects the end-to-end encryption option, theencryption device 104 proceeds to prepare the data packet 102, to embedthe selected message, based on a secure packet format 400 as shown inFIG. 4. Also, to proceed with the end-to-end encryption communication,the encryption device 104 is configured to then randomly generate asymmetric message encryption key (not shown) and a recipient infoencryption key (not shown), the purposes of which are elaborated below.In addition, a new unique set of message encryption key and recipientinfo encryption key is generated for each data packet 102 to betransmitted by the encryption device 104. It is further to beappreciated that the data packet 102 may be embedded as a payload of astandard IP packet.

Referring to FIG. 4, the packet format 400 includes seven data fields401-407 in total, although additional necessary data fields may be addedif required. Specifically, the seven data fields 401-407 include (basedon an arranged order of data sequence in the packet format 400): aversion-number field 401, an encrypted-message-key field 402, anencrypted-recipient-information-key field 403, an initialization-vectorfield 404, an encrypted-recipient-information field 405, anencrypted-message field 406, and a digital-signature 407 field. Tobriefly explain, the version-number field 401 defines a present versionof the packet format 400 in use, the encrypted-message-key field 402stores the message encryption key encrypted using the public key of thedecryption device 106, while the encrypted-recipient-information-keyfield 403 stores the recipient info encryption key encrypted using thepublic key of the server 108. For a scenario comprising multiple servers108, the encrypted-recipient-information-key field 403 stores therecipient info encryption key which is encrypted instead using thecommon public key accessible by all the servers 108, as afore explained.The initialization-vector field 404 defines a starting variable used forencryption (as will be appreciated by skilled persons), theencrypted-recipient-information field 405 stores identification data ofthe decryption device 106 encrypted using the recipient info encryptionkey, whereas the encrypted-message field 406 stores the selected messageencrypted using the message encryption key, and the digital-signaturefield 407 stores an authentication checksum generated based on theencrypted message (as stored in the encrypted-message field 406). It isto be appreciated that the identification data of the decryption device106 refers to associated location information, such as an IP address, ofthe decryption device 106, which would enable the server 108 toidentify, forward and route the data packet 102 from the encryptiondevice 104 to the decryption device 106. Thus, the identification datais location information associated with the recipient, since thedecryption device 106 is the recipient of the data packet 102 in thisinstance. It is to be appreciated that the encryption device 104 obtainsthe identification data of the decryption device 106, as distributed bythe server 108 through a separate communication channel/means, which isnot the focus of the discussion of the present invention.

It is to be appreciated that the software interface, displayed by thedisplay module 1046 of the encryption device 104, automaticallyseparates the identification data from the message (without requiringany user intervention), for the purpose of enabling the identificationdata to be encrypted separately from the message (which will also beencrypted). This is now'elaborated below.

Resuming our description of the method 300 in FIG. 3, at step 304, theencryption module 1042 (of the encryption device 104) encrypts theselected message and identification data of the decryption device 106respectively using the message encryption key and the recipient infoencryption key, and stores the encrypted message and identification datarespectively in the encrypted-message field 406 andencrypted-recipient-information field 405 (of the data packet 102). Acorresponding authentication checksum is also generated by the processormodule 10410 (of the encryption device 104) based on the encryptedmessage (using any suitable existing checksum algorithms), and stored inthe digital-signature field 407. Thereafter at step 306, the encryptionmodule 1042 (of the encryption device 104) encrypts the messageencryption key and the recipient info encryption key using respectivelythe public key of the decryption device 106, and the public key of theserver 108. It is to be appreciated that for a scenario which comprisesmultiple servers 108, the recipient info encryption key is insteadencrypted using the common public key accessible by all the servers 108,as above explained. The encrypted message encryption key, and recipientinfo encryption key are then respectively stored in theencrypted-message-key field 402 and encrypted-recipient-information-keyfield 403 (of the data packet 102). The data packet 102 is thenassembled into a complete form by the encryption device 104. At step308, the transmission module 1048 (of the encryption device 104)transmits the (assembled) data packet 102 to the server 108. It is to beappreciated that the data packet may be transmitted via suitable digitalmessaging schemes such as using an SMS, an MMS, instant messaging (IM),an email, an attachment, an electronic document delivery service or thelike.

The server 108 then performs a method 500 (as depicted in FIG. 5) forprocessing the data packet 102 that is received from the encryptiondevice 104, which permits true end-to-end encryption communicationbetween the encryption device 104 and decryption device 106. Inparticular, the server 108 first receives the data packet 102 via thereceiver module 1082 (of the server 108) at step 502. The server 108performs an authentication check using data retrieved from thedigital-signature field 407 of the received data packet 102 to ensurethat the encrypted message in the encrypted-message field 406 has notbeen tampered with at any point during transit from the encryptiondevice 104 to the server 108. Then, at step 504, the decryption module1084 of the server 108 is configured to decrypt the encrypted recipientinfo encryption key, as stored in theencrypted-recipient-information-key field 403 of the received datapacket 102, using the private key of the server 108. This allowsretrieval of the recipient info encryption key “in the clear” (i.e.unencrypted). It is to be appreciated that for a scenario whichcomprises multiple servers 108, the encrypted recipient info encryptionkey is instead decrypted using the common private key which isaccessible by all the servers 108, as already above explained.Thereafter, the decryption module 1084 of the server 108 proceeds todecrypt the encrypted identification data, as stored in theencrypted-recipient-information field 405 of the data packet 102, usingthe recipient info encryption key obtained in step 504. This allowsretrieval of the identification data “in the clear”. Once the server 108determines where the data packet 102 needs to be routed to next, basedon the identification data obtained in afore said step 506, thetransmission module 1086 of the server 108 then transmits and forwardsthe data packet 102 to the destination specified in the identificationdata. Of course, in the context of the current discussion, theidentification data is associated with the decryption device 106, andthus the data packet is to be forwarded to the decryption device 106.Importantly, it is to be appreciated that the data packet 102 isforwarded by the server 108 verbatim to the decryption device 106; thatis, the server 108 does not (in anyway) alter, re-encrypt or re-formatthe data packet 102 which it receives from the encryption device 104.

It is to be understood that during the performance of the method 500 ofFIG. 5, the server 108 will not be able to decrypt the encrypted-messagefield 406 and the encrypted-message-key field 402 of the data packet102. This is because the server 108 is not configured to have a copy ofthe private key of the decryption device 106, which is required in orderto decrypt the encrypted-message-key field 402. Only with retrieval ofthe message encryption key “in the clear” would enable theencrypted-message field 406 to be decrypted to obtain the message “inthe clear”. That is, the server 108 is unable to decrypt and access themessage intended for the decryption device 106, which beneficiallypermits secure end-to-end encryption communication between the senderand intended recipient.

FIG. 6 then depicts a method 600 performed by the decryption device 106for processing the data packet 102 received from the server 108. At step602, the receiver module 1062 (of the decryption device 106) receivesthe data packet 102 forwarded by the server 108, and at step 604, thedecryption module 1064 (of the decryption device 106) is configured todecrypt the encrypted-message-key field 402 of the data packet 102 toobtain the message encryption key “in the clear”. With successfulretrieval of the decrypted message encryption key, the decryption module1064 (of the decryption device 106) is then arranged to use the messageencryption key (obtained at step 604) to decrypt the encrypted-messagefield 406 of the data packet 102 to obtain the decrypted message at step606. The decryption device 106 may then access and read the message thatwas transmitted by the encryption device 104.

Further embodiments of the invention will be described hereinafter. Forthe sake of brevity, description of like elements, functionalities andoperations that are common between the embodiments are not repeated;reference will instead be made to similar parts of the relevantembodiment(s).

According to a second embodiment, in a scenario where there are multipledecryption devices 106 (i.e. more than one recipients for groupcommunications), the encryption module 1042 (of the encryption device104) encrypts the identification data of each decryption device 106using the recipient info encryption key associated with thecorresponding decryption device 106, thereafter stores all of theencrypted identification data into the encrypted-recipient-informationfield 405 of a new data packet 102 to be transmitted. In particular, allof the encrypted identification data are concatenated into a data stringwhich is stored into the encrypted-recipient-information field 405 ofthe new data packet 102. All the recipient info encryption keys of themultiple decryption devices 106 are then arranged to be encrypted (bythe encryption module 1042 of the encryption device 104) using thepublic key of the server 108, and collectively stored in theencrypted-recipient-information-key field 403 of the data packet 102.Furthermore, the encryption module 1042 (of the encryption device 104)also uses the public key of each decryption device 106 to encrypt themessage encryption key, which is then stored into theencrypted-message-key field 402 of the data packet 102. Morespecifically, the message encryption key is independently and singlyencrypted using the corresponding public key of each decryption device106 to form an associated encrypted message encryption key. As will beappreciated, this process is performed for the public keys of all thedecryption devices 106, and the resulting encrypted message encryptionkeys generated are then subsequently concatenated into a data string,that is stored into the encrypted-message-key field 402 of the datapacket 102. It is to be appreciated that in this embodiment, the steps302-308 in the method 300 of FIG. 3 are still performed similarly by theencryption device 104; only the type and amount of data stored in thedata packet 102 varies in respect of the first embodiment.

When the server 108 receives the data packet 102 transmitted by theencryption device 104, the decryption module 1084 of the server 108 thendecrypts the encrypted recipient info encryption key, as stored in theencrypted-recipient-information-key field 403 of the received datapacket 102, using the private key of the server 108. This enables theserver 108 to retrieve all the decrypted recipient info encryption keysof the multiple decryption devices 106, which are then furtherrespectively used to decrypt the corresponding segment of the datastring as stored in the encrypted-recipient-information field 405 of thedata packet 102 to obtain the decrypted identification data of all themultiple decryption devices 106. With the decrypted identification data,the server 108 is then able to re-route the data packet 102 to each ofthe intended decryption devices 106. When the data packet 102 isdelivered to each of the decryption devices 106, the respectivedecryption devices 106 then decrypts the corresponding encrypted messageencryption keys (stored in the data string in the encrypted-message-keyfield 402 of the received data packet 102) using the associated privatekeys of the respective decryption devices 106 to obtain a copy of themessage encryption key. With the message encryption key, each decryptiondevice 106 is able to decrypt the encrypted-message field 406 of thedata packet 102 to obtain the decrypted message. It is to be appreciatedthat in this embodiment, the steps 502-508 in the method 500 of FIG. 5are still performed similarly by the server 108. It is also further tobe appreciated that the server 108 does not need to re-encrypt themessage, and neither is the server 108 able to re-encrypt the message,for reasons already stated in the first embodiment and thus not repeatedfor brevity.

According to a third embodiment, in a slight variation to the firstembodiment, instead of the public key of the decryption device 106, thepublic key of the server 108 is now used to encrypt the messageencryption key at step 306 in the method 300 of FIG. 3 (as selected bythe user of the encryption device 104).

This means that the server 108 is then able to access the encryptedmessage, because the server 108 can subsequently decrypt the encryptedmessage encryption key using the private key of the server 108. Indeed,with retrieval of the message encryption key, the server 108 can thusdecrypt the encrypted message to access it. That is, this means that theuser of the encryption device 104 may also want the server 108 to begranted access to the contents of the encrypted message (e.g. forsecurity verification purposes). Other than the above said variation, itwill be appreciated that the remaining of the described details of thefirst embodiment apply to the third embodiment, with no other changes.

In summary, the proposed system 100 (and corresponding method) enablesrealisation and implementation of a multiple-key encryption scheme thatallows a sender to send encrypted messages to one or multiple recipientsby forwarding the encrypted messages through at least one (intermediate)server to perform the re-routing, but however does not permit the serverto have the ability to decrypt the encrypted messages. Thisadvantageously ensures that a true end-to-end encryption is maintainedand achieved between the sender and the recipient(s), without allowingthe server to actually decrypt the encrypted messages.

Also, the proposed system 100 is configured to allow the sender to makea determination on whether the sender wants the server to be able toaccess an encrypted message. If the sender wants the server to accessthe said encrypted message, the sender can select an option whereby thepublic key of the server may instead be used to encrypt the messageencryption key (i.e. the third embodiment). But, if the sender insteadwants a true end-to-end encryption, in which the server is unable todecrypt the encrypted message, then the first and second embodimentsapply.

To reiterate, the proposed system 100 and method enable true end-to-endencryption communication between the sender and multiple recipientsthrough the (at least one) server, in which the server is configured toroute (and archive) data packets arranged with customized secure packetformat having, multiple encryption fields. One of the encryption fieldsstores an encrypted message intended for the recipient by the sender,and the server is not able to decrypt and access the encrypted message(which is encrypted using a public key of the recipient). Specifically,the secure packet format defines information required by differentparties, either for the purpose of archival, re-routing or the actualintended recipient(s). The identification data of the recipient isencrypted to prevent unauthorized access to the recipient'sidentification information. Particularly, the data packet is encryptedusing a proposed multiple-key encryption scheme using a customizedencryption software application, and is transmitted to the recipient(s)via a digital messaging platform and is received by the recipient(s) onthe same type of digital messaging platform. To access the message, therecipient then decrypts the encrypted message (using the recipient's ownprivate key) to view the message. It will be appreciated that the serverreceives the same data packet in the process of forwarding the datapacket to the recipient, and is able to decrypt specific encryptionfields of the data packet, i.e. the encrypted-recipient-informationfield 405 of the data packet to determine whether to re-route the datapacket or to archive the data packet. However, the server is notconfigured with an encryption key (i.e. private key of the recipient)for decrypting the encrypted message stored in the data packet. Thisensures that in a digital messaging system, where the (intermediateforwarding) server performs a critical role for routing messages betweensenders and recipients, the server is not able to decrypt the encryptedmessage and access the associated content. Hence, the proposed systemenables a true end-to-end encryption system and scheme for the senderand recipients, but yet allows the server to participate in theforwarding/routing communications without compromising the security andauthenticity of the content of the encrypted message transmitted by thesender to the recipient.

To also broadly summarise the proposed method, there is disclosed amethod performed by at least one server for processing a data packetfrom a first computing device to be transmitted to a second computingdevice, wherein the data packet includes a message encrypted using afirst encryption key to form an encrypted message, identification dataof the second computing device encrypted using a second encryption keyto form encrypted identification data, an encrypted first encryption keyformed by encrypting the first encryption key using a third encryptionkey associated with the second computing device, and an encrypted secondencryption key formed by encrypting the second encryption key using anencryption key associated with the server. The method comprisesdecrypting the encrypted second encryption key; decrypting the encryptedidentification data using the decrypted second encryption key; andtransmitting the data packet based on the decrypted identification data.Specifically, the encrypted first encryption key is arranged to bedecryptable only using a fourth encryption key associated with thesecond computing device, wherein the third and fourth encryption keys ofthe second computing device are configured as a pair of asymmetric keys.That is, the pair of asymmetric keys comprises a public key (i.e. thethird encryption key) and a private key (i.e. the fourth encryption key)as per the established concept of public-key cryptography.

The described embodiments should not however be construed as limitative.For example, it is to be appreciated that the encryption and decryptiondevices 104, 106 may be any other types of suitable devices besidesmobile computing devices. Also, the respective modules of the encryptiondevice 104 and decryption device 106 (if implemented in software) may beprogrammatically integrated and provided as respective single, completesoftware applications that are installable on and executable by similarcomputing devices that may be envisaged for processing the data packet102. Optionally, the single complete software applications may beimplemented in entirety in hardware, and a copy of such an implementedhardware is incorporated on each of the encryption device 104 and thedecryption device 106. The alternative configurations described in theimmediate preceding two statements may also apply mutatis mutandis tothe said modules of the server 108. Moreover, alternatively, theencryption and decryption program codes may be stored on externalstorage devices, and are downloadable “on-demand” to be executed on theencryption device and decryption device 104, 106 respectively whenrequired. Further, in the software interface, as displayed by thedisplay module 1046 of the encryption device 104, an option to allow theuser to select the server 108 as the recipient, instead of thedecryption device 106, may also be displayed. It is also to beappreciated that for a scenario of multiple servers 108, the servers 18may be collectively configured with a set of load balancing rules whichdetermine where the data packet 102 is to be forwarded to. Further, thepacket format 400 as shown in FIG. 4 may be modified as necessary toinclude new data fields, or remove existing data fields, based onrequirements of an intended application.

While the invention has been illustrated and described in detail in thedrawings and foregoing description, such illustration and descriptionare to be considered illustrative or exemplary, and not restrictive; theinvention is not limited to the disclosed embodiments. Other variationsto the disclosed embodiments can be understood and effected by thoseskilled in the art in practising the claimed invention.

1. A method performed by at least one server for processing a datapacket from a first computing device to be transmitted to a secondcomputing device, wherein the data packet includes a message encryptedusing a first encryption key to form an encrypted message,identification data of the second computing device encrypted using asecond encryption key to form encrypted identification data, andencrypted first and second encryption keys, the method comprising:decrypting the encrypted second encryption key; decrypting the encryptedidentification data using the decrypted second encryption key; andtransmitting the data packet based on the decrypted identification data,wherein the encrypted message and first encryption key are arranged tobe undecryptable by the server to permit end-to-end encryptioncommunication between the first and second computing devices.
 2. Themethod of claim 1, wherein decrypting the encrypted second encryptionkey includes using a private key of the server to perform thedecryption. 3-4. (canceled)
 5. The method of claim 1, wherein the firstencryption key is encrypted using a public key of the second computingdevice.
 6. The method of claim 1, wherein the first encryption key isencrypted using a public key of the server.
 7. The method of claim 1,wherein the second encryption key is encrypted using a public key of theserver.
 8. The method of claim 1, wherein the data packet furtherincludes an initialization vector, and a digital signature generatedbased on the encrypted message.
 9. A method performed by a firstcomputing device for processing information to be transmitted to asecond computing device via at least one server to permit end-to-endencryption communication between the first and second computing devices,the method comprising: encrypting a message and identification data ofthe second computing device respectively using first and secondencryption keys; encrypting the first and second encryption keys; andtransmitting the encrypted message, identification data, first andsecond encryption keys collectively as a data packet. 10-11. (canceled)12. The method of claim 9, wherein encrypting the first encryption keyincludes encrypting using an encryption key of the second computingdevice, or an encryption key of the server.
 13. The method of claim 12,wherein the encryption key of the second computing device includes apublic key thereof.
 14. The method of claim 12, wherein the encryptionkey of the server includes a public key thereof.
 15. The method of claim9, wherein encrypting the second encryption key includes encryptingusing an encryption key of the server.
 16. The method of claim 15,wherein the encryption key of the server includes a public key thereof.17. The method of claim 9, further comprising displaying an interface toenable a user of the first computing device to select the message from aplurality of messages, and the second computing device from a pluralityof computing devices able to receive the data packet.
 18. The method ofclaim 9, wherein the data packet further includes an initializationvector, and a digital signature generated based on the encryptedmessage. 19-20. (canceled)
 21. A system for exchanging a data packetbetween first and second computing devices via at least one server topermit end-to-end encryption communication between the first and secondcomputing devices, the system comprising: the first computing devicewhich includes an encryption module for: encrypting a message andidentification data of the second computing device respectively usingfirst and second encryption keys; and encrypting the first and secondencryption keys; and a transmission module for transmitting theencrypted message, identification data, first and second encryption keyscollectively as the data packet to the server; the server configured toprocess the data packet received from the first computing device andincludes a decryption module for: decrypting the encrypted secondencryption key of the data packet; and decrypting the encryptedidentification data of the data packet using the decrypted secondencryption key; and a transmission module for transmitting the datapacket to the second computing device based on the decryptedidentification data, wherein the encrypted message and first encryptionkey are arranged to be undecryptable by the server; and the secondcomputing device configured to process the data packet received from theserver and includes a decryption module for: decrypting the encryptedfirst encryption key of the data packet; and decrypting the encryptedmessage of the data packet using the decrypted first encryption key toobtain the message. 22-31. (canceled)
 32. A method performed by at leastone server for processing a data packet from a first computing device tobe transmitted to a second computing device, wherein the data packetincludes a message encrypted using a first encryption key to form anencrypted message, identification data of the second computing deviceencrypted using a second encryption key to form encrypted identificationdata, an encrypted first encryption key formed by encrypting the firstencryption key using a third encryption key associated with the secondcomputing device, and an encrypted second encryption key formed byencrypting the second encryption key using an encryption key associatedwith the server, the method comprising: decrypting the encrypted secondencryption key; decrypting the encrypted identification data using thedecrypted second encryption key; and transmitting the data packet basedon the decrypted identification data, wherein the encrypted firstencryption key is arranged to be decryptable only using a fourthencryption key associated with the second computing device; and whereinthe third and fourth encryption keys of the second computing device areconfigured as a pair of asymmetric keys.
 33. The method of claim 32,wherein the encryption key associated with the server includes a publickey of the server.
 34. The method of claim 33, wherein decrypting theencrypted second encryption key includes using a private key of theserver to perform the decryption. 35-36. (canceled)
 37. The method ofclaim 32, wherein the third and fourth encryption keys respectivelyinclude a public key and a private key of the second computing device.38. The method of claim 32, wherein the data packet further includes aninitialization vector, and a digital signature generated based on theencrypted message.